Mechanism for facilitating dynamic format transformation of software applications in an on-demand services environment

ABSTRACT

In accordance with embodiments, there are provided mechanisms and methods for facilitating dynamic zero-downtime updating of formats of software applications in an on-demand services environment. In one embodiment and by way of example, a method includes receiving a request to facilitate a format change to a current version of a software application at a computing device, and retrieving a trigger corresponding to the format change, where a trigger may include a version indicator to indicate a past version of the software application relating to the format change. The method may further include comparing the current version and the indicated past version of the software application, and invoking the format change to the current version of the software application based on the retrieved trigger and the version indicator.

CLAIM OF PRIORITY

This application claims the benefit of U.S. Provisional Patent Application No. 61/528,517, entitled “Methods and Systems for Zero Downtime in an On-Demand Service Environment” by Karthik Rajan, filed Aug. 29, 2011, the entire contents of which are incorporated herein by reference and priority is claimed thereof.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.

TECHNICAL FIELD

One or more implementations relate generally to data management and, more specifically, to a mechanism for facilitating dynamic format transformation of software applications in an on-demand services environment.

BACKGROUND

It is well-known that making changes to a software application format can cause plenty of downtime that is expensive and inefficient. Although several attempts have been made to simplify this often complex process of updating software application formats, these attempts have not been successful in significantly reducing the downtime associated with the process.

The subject matter discussed in the background section should not be assumed to be prior art merely as a result of its mention in the background section. Similarly, a problem mentioned in the background section or associated with the subject matter of the background section should not be assumed to have been previously recognized in the prior art. The subject matter in the background section merely represents different approaches, which in and of themselves may also be inventions.

In conventional database systems, users access their data resources in one logical database. A user of such a conventional system typically retrieves data from and stores data on the system using the user's own systems. A user system might remotely access one of a plurality of server systems that might in turn access the database system. Data retrieval from the system might include the issuance of a query from the user system to the database system. The database system might process the request for information received in the query and send to the user system information relevant to the request. The secure and efficient retrieval of accurate information and subsequent delivery of this information to the user system has been and continues to be a goal of administrators of database systems. Unfortunately, conventional database approaches are associated with various limitations.

SUMMARY

In accordance with embodiments, there are provided mechanisms and methods for facilitating dynamic zero-downtime updating of formats of software applications in an on-demand services environment. In one embodiment and by way of example, a method includes receiving a request to facilitate a format change to a current version of a software application at a computing device, and retrieving a trigger corresponding to the format change, where a trigger may include a version indicator to indicate a past version of the software application relating to the format change. The method may further include comparing the current version and the indicated past version of the software application, and invoking the format change to the current version of the software application based on the retrieved trigger and the version indicator.

While the present invention is described with reference to an embodiment in which techniques for facilitating management of data in an on-demand services environment are implemented in a system having an application server providing a front end for an on-demand database service capable of supporting multiple tenants, the present invention is not limited to multi-tenant databases nor deployment on application servers. Embodiments may be practiced using other database architectures, i.e., ORACLE®, DB2® by IBM and the like without departing from the scope of the embodiments claimed.

Any of the above embodiments may be used alone or together with one another in any combination. Inventions encompassed within this specification may also include embodiments that are only partially mentioned or alluded to or are not mentioned or alluded to at all in this brief summary or in the abstract. Although various embodiments of the invention may have been motivated by various deficiencies with the prior art, which may be discussed or alluded to in one or more places in the specification, the embodiments of the invention do not necessarily address any of these deficiencies. In other words, different embodiments of the invention may address different deficiencies that may be discussed in the specification. Some embodiments may only partially address some deficiencies or just one deficiency that may be discussed in the specification, and some embodiments may not address any of these deficiencies.

BRIEF DESCRIPTION OF THE DRAWINGS

In the following drawings like reference numbers are used to refer to like elements. Although the following figures depict various examples, one or more implementations are not limited to the examples depicted in the figures.

FIG. 1 illustrates a computing system employing a dynamic format transformation mechanism according to one embodiment;

FIG. 2 illustrates a dynamic format transformation mechanism employed at a computing device according to one embodiment;

FIG. 3 illustrate a transaction sequence for performing zero-downtime updating of software application formats using a dynamic format transformation mechanism according to one embodiment;

FIG. 4 illustrates a method for dynamic zero-downtime updating of software application formats using a dynamic format transformation mechanism according to one embodiment;

FIG. 5 illustrates a computer system according to one embodiment;

FIG. 6 illustrates a block diagram of an environment wherein an on-demand database service might be used according to one embodiment; and

FIG. 7 illustrates a block diagram of an embodiment of elements of environment of FIG. 6 and various possible interconnections between these elements according to one embodiment.

DETAILED DESCRIPTION

Methods and systems are provided for facilitating dynamic zero-downtime updating of formats of software applications in an on-demand services environment. In one embodiment and by way of example, a method includes receiving a request to facilitate a format change to a current version of a software application at a computing device, and retrieving a trigger corresponding to the format change, where a trigger may include a version indicator to indicate a past version of the software application relating to the format change. The method may further include comparing the current version and the indicated past version of the software application, and invoking the format change to the current version of the software application based on the retrieved trigger and the version indicator.

As used herein, a term multi-tenant database system refers to those systems in which various elements of hardware and software of the database system may be shared by one or more customers. For example, a given application server may simultaneously process requests for a great number of customers, and a given database table may store rows for a potentially much greater number of customers. As used herein, the term query plan refers to a set of steps used to access information in a database system.

Next, mechanisms and methods for dynamically transforming or making changes to software application formats without requiring any downtime in an on-demand service environment having a multi-tenant database system will be described with reference to example embodiments.

FIG. 1 illustrates a computing system employing a dynamic format transformation mechanism according to one embodiment. In one embodiment, a computing device 100 serves as a host machine hosting a dynamic format transformation mechanism (“format mechanism”) 110 to facilitate dynamic, customized, and efficient updating of software application formats or version without having to require any downtime. Computing device 100 serving as a host machine may include server computers, desktop computers, cluster-based computers, laptop computing devices (e.g., notebooks, netbooks, etc.), set-top boxes (e.g., Internet-based cable television set-top boxes, etc.), and the like. Computing device 100 may also include mobile computing devices, such as cellular phones including smartphones (e.g., iPhone®, BlackBerry®, etc.), handheld computing devices, personal digital assistants (PDAs), etc., tablet computers (e.g., iPad®, Samsung® Galaxy Tab®, etc.), laptop computers, e-readers (e.g., Kindle®, Nook®, etc.), Global Positioning System (GPS)-based navigation systems, etc.

Computing device 100 includes an operating system 106 serving as an interface between any hardware or physical resources of the computer device 100 and a user. Computing device 100 further includes one or more processors 102, memory devices 104, network devices, drivers, or the like, as well as input/output (I/O) sources 108, such as touchscreens, touch panels, touch pads, virtual or regular keyboards, virtual or regular mice, etc. It is to be noted that terms like “node”, “computing node”, “client”, “client device”, “server”, “server device”, “machine”, “host machine”, “device”, “computing device”, “computer”, “computing system”, “multi-tenant on-demand data system”, and the like, are used interchangeably and synonymously throughout this document. It is to be further noted that terms like “application”, “software application”, “program”, “software program”, “package”, and “software package” are used interchangeably and synonymously throughout this document.

FIG. 2 illustrates a dynamic format transformation mechanism employed at a computing device according to one embodiment. In one embodiment, a dynamic format transformation mechanism 110, in communication with a database 214, includes various components 202, 204, 206, 208, 210 and 212 to offer a number of services to facilitate a zero-downtime updating of software applications from one format/version to another format/version in a multi-tenant database system in an on-demand services environment. The format mechanism 110 includes an access (maintenance) module 202 to stay in communication with the database 214 to be able to maintain as well as access a current version (e.g., version 4.0) and any number of past versions (e.g., versions 1.0, 2.0, 3.0, 3.0, etc.) of a software application stored at the database 214.

In one embodiment, the format mechanism 110 includes a reception module 204 to receive a request for a data change in the current format (e.g., a change in the way home addresses of customers are displayed, etc.) of a software application. The request may be received from a user at a computing device at an organization. A user may refer to an employee (e.g., salesperson, a database administrator, an account executive, etc.), a contractor, an intern, or the like, at an organization, where the organization refers to any vendor subscribing to the format mechanism 110, such as a profit-based company (e.g., a corporation, a small business, a law firm, a hospital, etc.), a government agency (e.g., a national or local government, an intelligence agency), an educational institution (e.g., an elementary school, a university, etc.), a non-profit organization (e.g., a non-government organization (NRO), etc.), and the like.

Once the request is received at the reception module 204, it facilitates a trigger retriever 206 to retrieve a relevant trigger to manipulate the relevant data format change between two or more versions of the software application to accommodate the user's request. In one embodiment, any number of triggers corresponding to such format updates may be created and placed in the database 214 and linked to the trigger retriever 206 such that the trigger retriever 206 remains aware of such triggers at the database 214 so that they can be retrieved and used as necessary. In one embodiment, each trigger may include a version indictor to identify one or more past versions (e.g., version 2.0, 1.0, etc.) of the software application that are to be accessed and referenced to facilitate the requested data format change to the current version (e.g., version 3.0) of the software application. This information is then provided to the access (maintenance) module 202 to access the database 214 to obtain the identified relevant past versions that are to be compared with the current version.

A comparison module 208 of the format mechanism 110 compares the two versions (e.g., the home address section of the two formats associated with the two versions) of the software application to determine the change that is to be made to satisfy the user's request. Once the comparison is completed, a trigger invocation (update) module 210 facilitates invoking the change to the current version of the software application based on the retrieved trigger and its version indicator, such as changing the home address format in the current version based on the customer home address information provided in the previous version as indicated by the version indicator as revealed by the retrieved trigger. This will be further described with reference to FIG. 3.

The format mechanism 110 further includes a compatibility module 212 that allows the format mechanism 110 to be dynamically and automatically compatible with any type of computer devices (e.g., computer device 100 of FIG. 1), software applications, software development platforms, application servers, interfaces (e.g., Graphical User Interface (GUI)-based interfaces, etc.), Internet or hotspot service providers (e.g., telecommunication companies, etc.), and the like. In this document, “version” refers to the assigned or published version of a software application, such as version 1.0, 2.2, 3.0, etc., while “format” refers to the format in which the data is used or presented or displayed a particular version of the software application. For example, in version 1.0 of a software application, customer names may be presented in the first name/last name format, while in version 2.0 of the same software application, those customer name may be displayed in the first name/middle name/last name format. It is to be noted that embodiments of the present invention are not limited to certain changes to a particular data set of a certain format or a particular format within a version or a particular version, but that they are compatible and workable with any number, type, and amount, etc., of data changes to be made to any software application formats and/or versions.

It is contemplated that any number and type of components may be added to and removed from the format mechanism 110 to facilitate efficient zero-downtime updating of software application formats. For brevity, clarity, ease of understanding and to stay focused on the format mechanism 110, many of the standard or known components, such as those of a computing device, are not shown or discussed here. It is contemplated that embodiments of the invention are not limited to any particular technology or standard and is dynamic enough to adopt and adapt to the changing technology and standards.

FIG. 3 illustrates a transaction sequence for performing zero-downtime updating of software application formats using a dynamic format transformation mechanism according to one embodiment. In the illustrated embodiment and for example, a software application is upgraded from version 1 302 to version 2 322. Version 1 302 includes two records 310A including record 1 312A and record 2 314B illustrating their first names 304, last names 306, and birthdates 308A. Now let us suppose, in one embodiment, the current running version of the software application is version 2 322 or that, in another embodiment, version 1 302 is to be upgraded to version 2 322. In either case, a user places an application invocation request (“request”) that the current name format of version 1 302 which lists the customers' first and last names 304, 306 be changed to a different format showing just the name 324A in version 2 322.

In one embodiment, as aforementioned in reference to FIG. 2, once the request to change the name format is received, an appropriate update trigger corresponding to the data format change is retrieved. The retrieved trigger includes a version indicator to point to (the previous) version 1 302 which includes both the first and last names 304, 306 of customers 312A, 314B. Based on the version indicator, version 1 302 is accessed at and obtained from a database and then compared with version 2 322. Upon completion of the comparison, the requested change is invoked. In one embodiment, upon invoking the change, the first and last names 304, 306 are obtained from version 1 302 and manipulated in version 2 322 to be presented as names 324A corresponding to records 1 312B and 2 314B of records 310B as requested by the user. The manipulation, in one embodiment, may be performed using a simple formula, such as name=first name+last name, that is created and placed in the database as part of the relevant trigger. In other words, when the change is invoked, it is the relevant trigger that is invoked to facilitate the necessary manipulation or calculation to reach the desired or requested result. Since, for example, no change was requested to the format relating to birthdates 308A of version 1 302, they continue to be similarly displayed as birthdates 308B in version 2 322. This way, any requested format change or transformation from version 1 302 to version 2 322 of the software application is performed efficiently, quickly, and without any downtime because the change is performed in runtime without having to stop the running of the software application and/or any of its relevant system components or apparatus (e.g., virtual machines, application servers, etc.).

Continuing with FIG. 3, now let us suppose, the user requests another change to the software application. For example, this time the user requests to include a middle name in names 324A of version 2 322 and change the birthdate 308B in version 2 322 to age 334 in version 2 322. Again, in one embodiment, it could be that version 2 322 is to be upgraded to version 3 332 or, in another embodiment, version 3 332 is the current version which needs to be changed. Assuming version 3 332 is the current running version, in case of the requested change to the name format to include middle names, since such information is not available in any of the previous two versions 1 302, 2 322, the user may choose to insert (e.g., type in) the middle names (such as M for record 1 312C and Ann for record 2 314C of records 310C) manually via an interface.

However, with regard to age 334, the since both versions 1 302 and 2 322 include information relating to birthdates 308A, 308B, a retrieved trigger may point to any one of the two versions 1 302 and 2 322 or, for example, by default, to the most recent previous version 2 322 to retrieve the birthdates 308B to be changed to age 334 in version 3 332. As aforementioned, a simple formula to convert birthdates 308B to age 334 may be included in the corresponding trigger so that when the trigger is invoked, the requested change automatically and dynamically made, such as calculating and showing the customers' 312C, 314C exact age 334 for the day (e.g., Jul. 1, 2011) when their records 310C are access and/or viewed. In one embodiment, these changes are made with zero downtime, such as in runtime without having to stop the software application from running or bringing down any servers or other computing devices.

FIG. 4 illustrates a method for dynamic zero-downtime updating of software application formats using a dynamic format transformation mechanism according to one embodiment. Method 400 may be performed by processing logic that may comprise hardware (e.g., circuitry, dedicated logic, programmable logic, microcode, etc.), software (such as instructions run on a processing device), or a combination thereof, such as firmware or functional circuitry within hardware devices. In one embodiment, method 400 is performed by the dynamic format transformation mechanism 110 of FIG. 1.

Method 400 begins at block 405 with maintaining and having access to multiple versions of a software application at a database in communication with the dynamic format transformation mechanism. At block 410, an application invocation request is received to employ a new version or facilitate a change to the current version of a software application. At block 415, a relevant trigger (having a version indicator to indicate or pointing to one or more relevant previous versions of the software application) is retrieved. At block 420, using the version indicator provided by the retrieved trigger, one or more relevant previous versions of the software application are accessed. At block 425, the current version of the software application is compared with the accessed one or more past versions of the software application. At block 430, the retrieved trigger is invoked to facilitate the requested change to the software application.

FIG. 5 illustrates a diagrammatic representation of a machine 500 in the exemplary form of a computer system, in accordance with one embodiment, within which a set of instructions, for causing the machine 500 to perform any one or more of the methodologies discussed herein, may be executed. Machine 500 is the same as or similar to computing device 100 of FIG. 1. In alternative embodiments, the machine may be connected (e.g., networked) to other machines in a Local Area Network (LAN), an intranet, an extranet, or the Internet. The machine may operate in the capacity of a server or a client machine in a client-server network environment, or as a peer machine in a peer-to-peer (or distributed) network environment or as a server or series of servers within an on-demand service environment, including an on-demand environment providing multi-tenant database storage services. Certain embodiments of the machine may be in the form of a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a server, a network router, switch or bridge, computing system, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines (e.g., computers) that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.

The exemplary computer system 500 includes a processor 502, a main memory 504 (e.g., read-only memory (ROM), flash memory, dynamic random access memory (DRAM) such as synchronous DRAM (SDRAM) or Rambus DRAM (RDRAM), etc., static memory such as flash memory, static random access memory (SRAM), volatile but high-data rate RAM, etc.), and a secondary memory 518 (e.g., a persistent storage device including hard disk drives and persistent multi-tenant data base implementations), which communicate with each other via a bus 530. Main memory 504 includes emitted execution data 524 (e.g., data emitted by a logging framework) and one or more trace preferences 523 which operate in conjunction with processing logic 526 and processor 502 to perform the methodologies discussed herein.

Processor 502 represents one or more general-purpose processing devices such as a microprocessor, central processing unit, or the like. More particularly, the processor 502 may be a complex instruction set computing (CISC) microprocessor, reduced instruction set computing (RISC) microprocessor, very long instruction word (VLIW) microprocessor, processor implementing other instruction sets, or processors implementing a combination of instruction sets. Processor 502 may also be one or more special-purpose processing devices such as an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital signal processor (DSP), network processor, or the like. Processor 502 is configured to execute the processing logic 526 for performing the operations and functionality of dynamic visual workflow mechanism 110 as described with reference to FIGS. 1 and 2 and other figures discussed herein.

The computer system 500 may further include a network interface card 508. The computer system 500 also may include a user interface 510 (such as a video display unit, a liquid crystal display (LCD), or a cathode ray tube (CRT)), an alphanumeric input device 512 (e.g., a keyboard), a cursor control device 514 (e.g., a mouse), and a signal generation device 516 (e.g., an integrated speaker). The computer system 500 may further include peripheral device 536 (e.g., wireless or wired communication devices, memory devices, storage devices, audio processing devices, video processing devices, etc. The computer system 500 may further include a Hardware based API logging framework 534 capable of executing incoming requests for services and emitting execution data responsive to the fulfillment of such incoming requests.

The secondary memory 518 may include a machine-readable storage medium (or more specifically a machine-accessible storage medium) 531 on which is stored one or more sets of instructions (e.g., software 522) embodying any one or more of the methodologies or functions of dynamic visual workflow mechanism 110 as described with reference to FIGS. 1 and 2 and other figures described herein. The software 522 may also reside, completely or at least partially, within the main memory 504 and/or within the processor 502 during execution thereof by the computer system 500, the main memory 504 and the processor 502 also constituting machine-readable storage media. The software 522 may further be transmitted or received over a network 520 via the network interface card 508. The machine-readable storage medium 531 may include transitory or non-transitory machine-readable storage media.

Portions of various embodiments of the present invention may be provided as a computer program product, which may include a computer-readable medium having stored thereon computer program instructions, which may be used to program a computer (or other electronic devices) to perform a process according to the embodiments of the present invention. The machine-readable medium may include, but is not limited to, floppy diskettes, optical disks, compact disk read-only memory (CD-ROM), and magneto-optical disks, ROM, RAM, erasable programmable read-only memory (EPROM), electrically EPROM (EEPROM), magnet or optical cards, flash memory, or other type of media/machine-readable medium suitable for storing electronic instructions.

The techniques shown in the figures can be implemented using code and data stored and executed on one or more electronic devices (e.g., an end station, a network element). Such electronic devices store and communicate (internally and/or with other electronic devices over a network) code and data using computer-readable media, such as non-transitory computer-readable storage media (e.g., magnetic disks; optical disks; random access memory; read only memory; flash memory devices; phase-change memory) and transitory computer-readable transmission media (e.g., electrical, optical, acoustical or other form of propagated signals—such as carrier waves, infrared signals, digital signals). In addition, such electronic devices typically include a set of one or more processors coupled to one or more other components, such as one or more storage devices (non-transitory machine-readable storage media), user input/output devices (e.g., a keyboard, a touchscreen, and/or a display), and network connections. The coupling of the set of processors and other components is typically through one or more busses and bridges (also termed as bus controllers). Thus, the storage device of a given electronic device typically stores code and/or data for execution on the set of one or more processors of that electronic device. Of course, one or more parts of an embodiment of the invention may be implemented using different combinations of software, firmware, and/or hardware.

FIG. 6 illustrates a block diagram of an environment 610 wherein an on-demand database service might be used. Environment 610 may include user systems 612, network 614, system 616, processor system 617, application platform 618, network interface 620, tenant data storage 622, system data storage 624, program code 626, and process space 628. In other embodiments, environment 610 may not have all of the components listed and/or may have other elements instead of, or in addition to, those listed above.

Environment 610 is an environment in which an on-demand database service exists. User system 612 may be any machine or system that is used by a user to access a database user system. For example, any of user systems 612 can be a handheld computing device, a mobile phone, a laptop computer, a work station, and/or a network of computing devices. As illustrated in herein FIG. 6 (and in more detail in FIG. 7) user systems 612 might interact via a network 614 with an on-demand database service, which is system 616.

An on-demand database service, such as system 616, is a database system that is made available to outside users that do not need to necessarily be concerned with building and/or maintaining the database system, but instead may be available for their use when the users need the database system (e.g., on the demand of the users). Some on-demand database services may store information from one or more tenants stored into tables of a common database image to form a multi-tenant database system (MTS). Accordingly, “on-demand database service 616” and “system 616” will be used interchangeably herein. A database image may include one or more database objects. A relational database management system (RDMS) or the equivalent may execute storage and retrieval of information against the database object(s). Application platform 618 may be a framework that allows the applications of system 616 to run, such as the hardware and/or software, e.g., the operating system. In an embodiment, on-demand database service 616 may include an application platform 618 that enables creation, managing and executing one or more applications developed by the provider of the on-demand database service, users accessing the on-demand database service via user systems 612, or third party application developers accessing the on-demand database service via user systems 612.

The users of user systems 612 may differ in their respective capacities, and the capacity of a particular user system 612 might be entirely determined by permissions (permission levels) for the current user. For example, where a salesperson is using a particular user system 612 to interact with system 616, that user system has the capacities allotted to that salesperson. However, while an administrator is using that user system to interact with system 616, that user system has the capacities allotted to that administrator. In systems with a hierarchical role model, users at one permission level may have access to applications, data, and database information accessible by a lower permission level user, but may not have access to certain applications, database information, and data accessible by a user at a higher permission level. Thus, different users will have different capabilities with regard to accessing and modifying application and database information, depending on a user's security or permission level.

Network 614 is any network or combination of networks of devices that communicate with one another. For example, network 614 can be any one or any combination of a LAN (local area network), WAN (wide area network), telephone network, wireless network, point-to-point network, star network, token ring network, hub network, or other appropriate configuration. As the most common type of computer network in current use is a TCP/IP (Transfer Control Protocol and Internet Protocol) network, such as the global internetwork of networks often referred to as the “Internet” with a capital “I,” that network will be used in many of the examples herein. However, it should be understood that the networks that one or more implementations might use are not so limited, although TCP/IP is a frequently implemented protocol.

User systems 612 might communicate with system 616 using TCP/IP and, at a higher network level, use other common Internet protocols to communicate, such as HTTP, FTP, AFS, WAP, etc. In an example where HTTP is used, user system 612 might include an HTTP client commonly referred to as a “browser” for sending and receiving HTTP messages to and from an HTTP server at system 616. Such an HTTP server might be implemented as the sole network interface between system 616 and network 614, but other techniques might be used as well or instead. In some implementations, the interface between system 616 and network 614 includes load sharing functionality, such as round-robin HTTP request distributors to balance loads and distribute incoming HTTP requests evenly over a plurality of servers. At least as for the users that are accessing that server, each of the plurality of servers has access to the MTS′ data; however, other alternative configurations may be used instead.

In one embodiment, system 616, shown in FIG. 6, implements a web-based customer relationship management (CRM) system. For example, in one embodiment, system 616 includes application servers configured to implement and execute CRM software applications as well as provide related data, code, forms, webpages and other information to and from user systems 612 and to store to, and retrieve from, a database system related data, objects, and Webpage content. With a multi-tenant system, data for multiple tenants may be stored in the same physical database object, however, tenant data typically is arranged so that data of one tenant is kept logically separate from that of other tenants so that one tenant does not have access to another tenant's data, unless such data is expressly shared. In certain embodiments, system 616 implements applications other than, or in addition to, a CRM application. For example, system 616 may provide tenant access to multiple hosted (standard and custom) applications, including a CRM application. User (or third party developer) applications, which may or may not include CRM, may be supported by the application platform 618, which manages creation, storage of the applications into one or more database objects and executing of the applications in a virtual machine in the process space of the system 616.

One arrangement for elements of system 616 is shown in FIG. 6, including a network interface 620, application platform 618, tenant data storage 622 for tenant data 623, system data storage 624 for system data 625 accessible to system 616 and possibly multiple tenants, program code 626 for implementing various functions of system 616, and a process space 628 for executing MTS system processes and tenant-specific processes, such as running applications as part of an application hosting service. Additional processes that may execute on system 616 include database indexing processes.

Several elements in the system shown in FIG. 6 include conventional, well-known elements that are explained only briefly here. For example, each user system 612 could include a desktop personal computer, workstation, laptop, PDA, cell phone, or any wireless access protocol (WAP) enabled device or any other computing device capable of interfacing directly or indirectly to the Internet or other network connection. User system 612 typically runs an HTTP client, e.g., a browsing program, such as Microsoft's Internet Explorer browser, Netscape's Navigator browser, Opera's browser, or a WAP-enabled browser in the case of a cell phone, PDA or other wireless device, or the like, allowing a user (e.g., subscriber of the multi-tenant database system) of user system 612 to access, process and view information, pages and applications available to it from system 616 over network 614. Each user system 612 also typically includes one or more user interface devices, such as a keyboard, a mouse, trackball, touch pad, touch screen, pen or the like, for interacting with a graphical user interface (GUI) provided by the browser on a display (e.g., a monitor screen, LCD display, etc.) in conjunction with pages, forms, applications and other information provided by system 616 or other systems or servers. For example, the user interface device can be used to access data and applications hosted by system 616, and to perform searches on stored data, and otherwise allow a user to interact with various GUI pages that may be presented to a user. As discussed above, embodiments are suitable for use with the Internet, which refers to a specific global internetwork of networks. However, it should be understood that other networks can be used instead of the Internet, such as an intranet, an extranet, a virtual private network (VPN), a non-TCP/IP based network, any LAN or WAN or the like.

According to one embodiment, each user system 612 and all of its components are operator configurable using applications, such as a browser, including computer code run using a central processing unit such as an Intel Pentium® processor or the like. Similarly, system 616 (and additional instances of an MTS, where more than one is present) and all of their components might be operator configurable using application(s) including computer code to run using a central processing unit such as processor system 617, which may include an Intel Pentium® processor or the like, and/or multiple processor units. A computer program product embodiment includes a machine-readable storage medium (media) having instructions stored thereon/in which can be used to program a computer to perform any of the processes of the embodiments described herein. Computer code for operating and configuring system 616 to intercommunicate and to process webpages, applications and other data and media content as described herein are preferably downloaded and stored on a hard disk, but the entire program code, or portions thereof, may also be stored in any other volatile or non-volatile memory medium or device as is well known, such as a ROM or RAM, or provided on any media capable of storing program code, such as any type of rotating media including floppy disks, optical discs, digital versatile disk (DVD), compact disk (CD), microdrive, and magneto-optical disks, and magnetic or optical cards, nanosystems (including molecular memory ICs), or any type of media or device suitable for storing instructions and/or data. Additionally, the entire program code, or portions thereof, may be transmitted and downloaded from a software source over a transmission medium, e.g., over the Internet, or from another server, as is well known, or transmitted over any other conventional network connection as is well known (e.g., extranet, VPN, LAN, etc.) using any communication medium and protocols (e.g., TCP/IP, HTTP, HTTPS, Ethernet, etc.) as are well known. It will also be appreciated that computer code for implementing embodiments can be implemented in any programming language that can be executed on a client system and/or server or server system such as, for example, C, C++, HTML, any other markup language, Java™, JavaScript, ActiveX, any other scripting language, such as VBScript, and many other programming languages as are well known may be used. (Java™ is a trademark of Sun Microsystems, Inc.).

According to one embodiment, each system 616 is configured to provide webpages, forms, applications, data and media content to user (client) systems 612 to support the access by user systems 612 as tenants of system 616. As such, system 616 provides security mechanisms to keep each tenant's data separate unless the data is shared. If more than one MTS is used, they may be located in close proximity to one another (e.g., in a server farm located in a single building or campus), or they may be distributed at locations remote from one another (e.g., one or more servers located in city A and one or more servers located in city B). As used herein, each MTS could include one or more logically and/or physically connected servers distributed locally or across one or more geographic locations. Additionally, the term “server” is meant to include a computer system, including processing hardware and process space(s), and an associated storage system and database application (e.g., OODBMS or RDBMS) as is well known in the art. It should also be understood that “server system” and “server” are often used interchangeably herein. Similarly, the database object described herein can be implemented as single databases, a distributed database, a collection of distributed databases, a database with redundant online or offline backups or other redundancies, etc., and might include a distributed database or storage network and associated processing intelligence.

FIG. 7 also illustrates environment 610. However, in FIG. 7 elements of system 616 and various interconnections in an embodiment are further illustrated. FIG. 7 shows that user system 612 may include processor system 612A, memory system 612B, input system 612C, and output system 612D. FIG. 7 shows network 614 and system 616. FIG. 7 also shows that system 616 may include tenant data storage 622, tenant data 623, system data storage 624, system data 625, User Interface (UI) 730, Application Program Interface (API) 732, PL/SOQL 734, save routines 736, application setup mechanism 738, applications servers 700 ₁-700 _(N), system process space 702, tenant process spaces 704, tenant management process space 710, tenant storage area 712, user storage 714, and application metadata 716. In other embodiments, environment 610 may not have the same elements as those listed above and/or may have other elements instead of, or in addition to, those listed above.

User system 612, network 614, system 616, tenant data storage 622, and system data storage 624 were discussed above in FIG. 6. Regarding user system 612, processor system 612A may be any combination of one or more processors. Memory system 612B may be any combination of one or more memory devices, short term, and/or long term memory. Input system 612C may be any combination of input devices, such as one or more keyboards, mice, trackballs, scanners, cameras, and/or interfaces to networks. Output system 612D may be any combination of output devices, such as one or more monitors, printers, and/or interfaces to networks. As shown by FIG. 7, system 616 may include a network interface 620 (of FIG. 6) implemented as a set of HTTP application servers 700, an application platform 618, tenant data storage 622, and system data storage 624. Also shown is system process space 702, including individual tenant process spaces 704 and a tenant management process space 710. Each application server 700 may be configured to tenant data storage 622 and the tenant data 623 therein, and system data storage 624 and the system data 625 therein to serve requests of user systems 612. The tenant data 623 might be divided into individual tenant storage areas 712, which can be either a physical arrangement and/or a logical arrangement of data. Within each tenant storage area 712, user storage 714 and application metadata 716 might be similarly allocated for each user. For example, a copy of a user's most recently used (MRU) items might be stored to user storage 714. Similarly, a copy of MRU items for an entire organization that is a tenant might be stored to tenant storage area 712. A UI 730 provides a user interface and an API 732 provides an application programmer interface to system 616 resident processes to users and/or developers at user systems 612. The tenant data and the system data may be stored in various databases, such as one or more Oracle™ databases.

Application platform 618 includes an application setup mechanism 738 that supports application developers' creation and management of applications, which may be saved as metadata into tenant data storage 622 by save routines 736 for execution by subscribers as one or more tenant process spaces 704 managed by tenant management process 710 for example. Invocations to such applications may be coded using PL/SOQL 734 that provides a programming language style interface extension to API 732. A detailed description of some PL/SOQL language embodiments is discussed in commonly owned U.S. Pat. No. 7,730,478 entitled, “Method and System for Allowing Access to Developed Applicants via a Multi-Tenant Database On-Demand Database Service”, issued Jun. 1, 2010 to Craig Weissman, which is incorporated in its entirety herein for all purposes. Invocations to applications may be detected by one or more system processes, which manage retrieving application metadata 716 for the subscriber making the invocation and executing the metadata as an application in a virtual machine.

Each application server 700 may be communicably coupled to database systems, e.g., having access to system data 625 and tenant data 623, via a different network connection. For example, one application server 700 ₁ might be coupled via the network 614 (e.g., the Internet), another application server 700 _(N-1) might be coupled via a direct network link, and another application server 700 _(N) might be coupled by yet a different network connection. Transfer Control Protocol and Internet Protocol (TCP/IP) are typical protocols for communicating between application servers 700 and the database system. However, it will be apparent to one skilled in the art that other transport protocols may be used to optimize the system depending on the network interconnect used.

In certain embodiments, each application server 700 is configured to handle requests for any user associated with any organization that is a tenant. Because it is desirable to be able to add and remove application servers from the server pool at any time for any reason, there is preferably no server affinity for a user and/or organization to a specific application server 700. In one embodiment, therefore, an interface system implementing a load balancing function (e.g., an F5 Big-IP load balancer) is communicably coupled between the application servers 700 and the user systems 612 to distribute requests to the application servers 700. In one embodiment, the load balancer uses a least connections algorithm to route user requests to the application servers 700. Other examples of load balancing algorithms, such as round robin and observed response time, also can be used. For example, in certain embodiments, three consecutive requests from the same user could hit three different application servers 700, and three requests from different users could hit the same application server 700. In this manner, system 616 is multi-tenant, wherein system 616 handles storage of, and access to, different objects, data and applications across disparate users and organizations.

As an example of storage, one tenant might be a company that employs a sales force where each salesperson uses system 616 to manage their sales process. Thus, a user might maintain contact data, leads data, customer follow-up data, performance data, goals and progress data, etc., all applicable to that user's personal sales process (e.g., in tenant data storage 622). In an example of a MTS arrangement, since all of the data and the applications to access, view, modify, report, transmit, calculate, etc., can be maintained and accessed by a user system having nothing more than network access, the user can manage his or her sales efforts and cycles from any of many different user systems. For example, if a salesperson is visiting a customer and the customer has Internet access in their lobby, the salesperson can obtain critical updates as to that customer while waiting for the customer to arrive in the lobby.

While each user's data might be separate from other users' data regardless of the employers of each user, some data might be organization-wide data shared or accessible by a plurality of users or all of the users for a given organization that is a tenant. Thus, there might be some data structures managed by system 616 that are allocated at the tenant level while other data structures might be managed at the user level. Because an MTS might support multiple tenants including possible competitors, the MTS should have security protocols that keep data, applications, and application use separate. Also, because many tenants may opt for access to an MTS rather than maintain their own system, redundancy, up-time, and backup are additional functions that may be implemented in the MTS. In addition to user-specific data and tenant specific data, system 616 might also maintain system level data usable by multiple tenants or other data. Such system level data might include industry reports, news, postings, and the like that are sharable among tenants.

In certain embodiments, user systems 612 (which may be client systems) communicate with application servers 700 to request and update system-level and tenant-level data from system 616 that may require sending one or more queries to tenant data storage 622 and/or system data storage 624. System 616 (e.g., an application server 700 in system 616) automatically generates one or more SQL statements (e.g., one or more SQL queries) that are designed to access the desired information. System data storage 624 may generate query plans to access the requested data from the database.

Each database can generally be viewed as a collection of objects, such as a set of logical tables, containing data fitted into predefined categories. A “table” is one representation of a data object, and may be used herein to simplify the conceptual description of objects and custom objects. It should be understood that “table” and “object” may be used interchangeably herein. Each table generally contains one or more data categories logically arranged as columns or fields in a viewable schema. Each row or record of a table contains an instance of data for each category defined by the fields. For example, a CRM database may include a table that describes a customer with fields for basic contact information such as name, address, phone number, fax number, etc. Another table might describe a purchase order, including fields for information such as customer, product, sale price, date, etc. In some multi-tenant database systems, standard entity tables might be provided for use by all tenants. For CRM database applications, such standard entities might include tables for Account, Contact, Lead, and Opportunity data, each containing pre-defined fields. It should be understood that the word “entity” may also be used interchangeably herein with “object” and “table”.

In some multi-tenant database systems, tenants may be allowed to create and store custom objects, or they may be allowed to customize standard entities or objects, for example by creating custom fields for standard objects, including custom index fields. U.S. patent application Ser. No. 10/817,161, filed Apr. 2, 2004, entitled “Custom Entities and Fields in a Multi-Tenant Database System”, and which is hereby incorporated herein by reference, teaches systems and methods for creating custom objects as well as customizing standard objects in a multi-tenant database system. In certain embodiments, for example, all custom entity data rows are stored in a single multi-tenant physical table, which may contain multiple logical tables per organization. It is transparent to customers that their multiple “tables” are in fact stored in one large table or that their data may be stored in the same table as the data of other customers.

While one or more implementations have been described by way of example and in terms of the specific embodiments, it is to be understood that one or more implementations are not limited to the disclosed embodiments. To the contrary, it is intended to cover various modifications and similar arrangements as would be apparent to those skilled in the art. Therefore, the scope of the appended claims should be accorded the broadest interpretation so as to encompass all such modifications and similar arrangements. It is to be understood that the above description is intended to be illustrative, and not restrictive. 

What is claimed is:
 1. A method comprising: receiving, at a first computing device, an invocation request to facilitate a format change to a software application, wherein the format change includes upgrading of one or more data formats of the software application such that a first version the software application is upgraded to a second version, wherein the invocation request is received from a user via a second computing device; dynamically retrieving, in response to the invocation request, a trigger from a plurality of triggers, wherein the trigger specifically relates to the invocation request for facilitating the format change and includes an indicator to indicate the one or more data formats of the first version; and invoking, in runtime, the retrieved trigger to perform the format change, wherein performing the format change includes manipulating, based on the indicator, the one or more data formats such that the first version is updated to the second version during runtime and without having to pause the software application.
 2. The method of claim 1, further comprising maintaining, at a database, a plurality of version indicators corresponding to a plurality of versions relating to a plurality of data formats of the software application, wherein the plurality of version indicators include the version indicator of the retrieved trigger, the plurality of versions include the first and second versions, and the plurality of data formats include the one or more data formats.
 3. The method of claim 1, further comprising accessing the first version of the software application at the database in response to discovering the version indicator of the retrieved trigger.
 4. The method of claim 1, wherein the one or more data formats comprise one or more segments of data or displaying of the data associated with the software application.
 5. The method of claim 1, wherein the first and second computing device comprise one or more of a server computer, a laptop computer, a smartphone, a personal digital assistant (PDA), a handheld computer, an e-reader, a tablet computer, a notebook, a desktop computer, a cluster-based computer, a set-top box, and a Global Positioning System (GPS)-based navigation system.
 6. A system comprising: a computing device having a memory to store instructions, and a processing device to execute the instructions, wherein the instructions cause the processing device to: receive, at a first computing device, an invocation request to facilitate a format change to a software application, wherein the format change includes upgrading of one or more data formats of the software application such that a first version the software application is upgraded to a second version, wherein the invocation request is received from a user via a second computing device; dynamically retrieve, in response to the invocation request, a trigger from a plurality of triggers, wherein the trigger specifically relates to the invocation request for facilitating the format change and includes an indicator to indicate the one or more data formats of the first version; and invoke, in runtime, the retrieved trigger to perform the format change, wherein performing the format change includes manipulating, based on the indicator, the one or more data formats such that the first version is updated to the second version during runtime and without having to pause the software application.
 7. The system of claim 6, wherein the processing device is further to maintain, at a database, a plurality of version indicators corresponding to a plurality of versions relating to a plurality of data formats of the software application, wherein the plurality of version indicators include the version indicator of the retrieved trigger, the plurality of versions include the first and second versions, and the plurality of data formats include the one or more data formats.
 8. The system of claim 6, wherein the processing device is further to access the first version of the software application at the database in response to discovering the version indicator of the retrieved trigger.
 9. The system of claim 6, wherein the one or more data formats comprise one or more segments of data or displaying of the data associated with the software application.
 10. The system of claim 6, wherein the first and second computing device comprise one or more of a server computer, a laptop computer, a smartphone, a personal digital assistant (PDA), a handheld computer, an e-reader, a tablet computer, a notebook, a desktop computer, a cluster-based computer, a set-top box, and a Global Positioning System (GPS)-based navigation system.
 11. A non-transitory machine-readable medium having stored thereon instructions which, when executed by a machine, cause the machine to: receive, at a first computing device, an invocation request to facilitate a format change to a software application, wherein the format change includes upgrading of one or more data formats of the software application such that a first version of the software application is upgraded to a second version, wherein the invocation request is received from a user via a second computing device; dynamically retrieve, in response to the invocation request, a trigger from a plurality of triggers, wherein the trigger specifically relates to the invocation request for facilitating the format change and includes an indicator to indicate the one or more formats of the first version; and invoke, in runtime, the retrieved trigger to perform the format change, wherein performing the format change includes manipulating, based on the indicator, the one or more data formats such that the first version is updated to the second version during runtime and without having to pause the software application.
 12. The non-transitory machine-readable medium of claim 11, wherein the machine is further to maintain, at a database, a plurality of version indicators corresponding to a plurality of versions relating to a plurality of data formats of the software application, wherein the plurality of version indicators include the version indicator of the retrieved trigger, the plurality of versions include the first and second versions, and the plurality of data formats include the one or more data formats.
 13. The non-transitory machine-readable medium of claim 11, wherein the machine is further to access the first version of the software application at the database in response to discovering the version indicator of the retrieved trigger.
 14. The non-transitory machine-readable medium of claim 11, wherein the one or more data formats comprise one or more segments of data or displaying of the data associated with the software application.
 15. The non-transitory machine-readable medium of claim 11, wherein the first and second computing device comprise one or more of a server computer, a laptop computer, a smartphone, a personal digital assistant (PDA), a handheld computer, an e-reader, a tablet computer, a notebook, a desktop computer, a cluster-based computer, a set-top box, and a Global Positioning System (GPS)-based navigation system. 